In article <CnDGr5.DGE@ucdavis.edu> ez003190@dale.ucdavis.edu (Jimmy Ip) writes:
>I am running trumpet winsock to a slip connection to a SparcII running
>SunOS 4.1.3. With the xwindemo (microx) I am trying to have an xterm
>display it on my pc over the modem.
>
>How can it make my pc "friendly" to the Sparc station, so that my
>pc will allow the xterm from the sparc to be displayed on my pc ?
Actually, you are dealing with a "feature" of X, not anything
special with winsock, slip, or xwindemo. You need to tell xterm
*where* the window is to appear. You can either use the -display
option on the command line or (what I do) set the environment
variable DISPLAY to your IP address (my.ip.addr.ess:0.0) (Remember
that 0.0).
--
Mike Lipsie (work) mlipsie@ca.merl.com
Mitsubishi Electric Research Laboratory (home) mikel@dosbears.UUCP
From wayne@cayman.Cayman.COM Mon Mar 28 12:39:11 1994
Received: from cayman.Cayman.COM by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AA15986; Mon, 28 Mar 1994 17:41:17 -0500
Received: from cuba.Cayman.COM (cuba.Cayman.COM [143.137.50.12]) by cayman.Cayman.COM (8.6.4/ECB-1.3) with SMTP id RAA20789 for <winsock@SunSITE.Unc.EDU>; Mon, 28 Mar 1994 17:40:36 -0500
Received: from Trinidad by cuba.Cayman.COM (4.1/SMI-4.1)
id AA15108; Mon, 28 Mar 94 17:40:36 EST
Message-Id: <9403282240.AA15108@cuba.Cayman.COM>
X-Sender: wayne@cuba
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 28 Mar 1994 17:39:11 -0500
To: winsock@SunSITE.Unc.EDU
From: wayne@Cayman.COM (Wayne F. Tackabury)
Subject: Winsock v.2 questions
X-Mailer: <PC Eudora Version 1.4b18>
My apologies if the following questions have been answered in detail...I've
been away from the list for a few weeks. All have to do with the promise,
power, and passion of Version 2 Winsock.
1. So Winsock over IPX is *definitely* in, right? Has anybody else
implemented this prior to v.2? Is this actually such a big deal
interface-wise, or are all the required SAP calls covered by available
GetXByY() semantics?
2. Has anybody independently set a target date for V.2 specification
availability? Product interoperability doability?
3. What are the issues in v.2 currently causing debate and consternation in
the community? I remember something about Winsock-over-OSI as a bit of a
bear to pin down, but I lost track of that argument, and don't know if any
other came to take its place.
4. (somewhat related) some time ago, I sent Martin Hall a rambling set of
suggestions for Winsock v.2, one of which (application capability to change
local host transport address) I now realize is covered in Berkeley Sockets
under the "interfaces" IOCTL family (along with ARP cache management,
getting the mask values, etc.). Has this family, or any other family of
IOCTLs not currently spec'ed in 1.0a, been identified for v.2 inclusion?
Thanks in advance!!
-- Wayne
----------------------------------
Wayne F. Tackabury Cayman Systems, Inc.
400 Unicorn Park Dr., Woburn MA 01801 Internet: wayne@cayman.com